Technologies for providing latency-aware consensus management in a disaggregated architecture

ABSTRACT

Technologies for providing latency-aware consensus management in a disaggregated system include a compute device. The compute device includes circuitry to determine latencies associated with subsystems of the disaggregated system. Additionally, the circuitry is to determine, as a function of the determined latencies, a time period in which a configuration change to the disaggregated system is to reach a consistent state in the subsystems.

BACKGROUND

In some data centers in which operations are performed on behalf of customers (e.g., tenants), resources are organized in a disaggregated architecture in which sets of resources (e.g., compute devices, accelerator devices, data storage devices, etc.) are physically separate from each other (e.g., a compute device may be in a separate circuit board than an accelerator device). In operation, a compute device may discover available resources in the system and allocated (e.g., “compose”) them into a group to cooperatively execute a workload (e.g., a set of operations, such as an application executed on behalf of a tenant). In composing a group (e.g., a node) of resources to execute a workload, sets of configuration changes may be communicated to the resources to change their operation (e.g., to enable them to interoperate as a node). Due to differences in processing time (e.g., latencies) for the resources to implement the configuration changes, it is possible for one set of resources of the node to adapt to the configuration change before another set of resources adapt to the change. Further, if instructions (e.g., control instructions) are to be implemented by the node before all of the resources have adapted to the configuration change (e.g., before a consistent state, also referred to as a consensus, has been reached), the node may operate incorrectly or inefficiently.

BRIEF DESCRIPTION OF THE DRAWINGS

The concepts described herein are illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. Where considered appropriate, reference labels have been repeated among the figures to indicate corresponding or analogous elements.

FIG. 1 is a simplified diagram of at least one embodiment of a data center for executing workloads with disaggregated resources;

FIG. 2 is a simplified diagram of at least one embodiment of a pod that may be included in the data center of FIG. 1;

FIG. 3 is a perspective view of at least one embodiment of a rack that may be included in the pod of FIG. 2;

FIG. 4 is a side elevation view of the rack of FIG. 3;

FIG. 5 is a perspective view of the rack of FIG. 3 having a sled mounted therein;

FIG. 6 is a is a simplified block diagram of at least one embodiment of a top side of the sled of FIG. 5;

FIG. 7 is a simplified block diagram of at least one embodiment of a bottom side of the sled of FIG. 6;

FIG. 8 is a simplified block diagram of at least one embodiment of a compute sled usable in the data center of FIG. 1;

FIG. 9 is a top perspective view of at least one embodiment of the compute sled of FIG. 8;

FIG. 10 is a simplified block diagram of at least one embodiment of an accelerator sled usable in the data center of FIG. 1;

FIG. 11 is a top perspective view of at least one embodiment of the accelerator sled of FIG. 10;

FIG. 12 is a simplified block diagram of at least one embodiment of a storage sled usable in the data center of FIG. 1;

FIG. 13 is a top perspective view of at least one embodiment of the storage sled of FIG. 12;

FIG. 14 is a simplified block diagram of at least one embodiment of a memory sled usable in the data center of FIG. 1;

FIG. 15 is a simplified block diagram of a system that may be established within the data center of FIG. 1 to execute workloads with managed nodes composed of disaggregated resources;

FIG. 16 is a simplified diagram of at least one embodiment of a system for providing latency-aware consensus management in the data center of FIG. 1;

FIGS. 17-20 are simplified block diagrams of at least one embodiment of a method for providing latency-aware consensus management that may be performed by a compute device of the system of FIG. 16; and

FIG. 21 is a simplified diagram of communications between components of at least one embodiment of a system for providing latency-aware consensus management in the data center of FIG. 1.

DETAILED DESCRIPTION

While the concepts of the present disclosure are susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and will be described herein in detail. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives consistent with the present disclosure and the appended claims.

References in the specification to “one embodiment,” “an embodiment,” “an illustrative embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may or may not necessarily include that particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. Additionally, it should be appreciated that items included in a list in the form of “at least one A, B, and C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C). Similarly, items listed in the form of “at least one of A, B, or C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).

The disclosed embodiments may be implemented, in some cases, in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried by or stored on a transitory or non-transitory machine-readable (e.g., computer-readable) storage medium, which may be read and executed by one or more processors. A machine-readable storage medium may be embodied as any storage device, mechanism, or other physical structure for storing or transmitting information in a form readable by a machine (e.g., a volatile or nonvolatile memory, a media disc, or other media device).

In the drawings, some structural or method features may be shown in specific arrangements and/or orderings. However, it should be appreciated that such specific arrangements and/or orderings may not be required. Rather, in some embodiments, such features may be arranged in a different manner and/or order than shown in the illustrative figures. Additionally, the inclusion of a structural or method feature in a particular figure is not meant to imply that such feature is required in all embodiments and, in some embodiments, may not be included or may be combined with other features.

Referring now to FIG. 1, a data center 100 in which disaggregated resources may cooperatively execute one or more workloads (e.g., applications on behalf of customers) includes multiple pods 110, 120, 130, 140, each of which includes one or more rows of racks. Of course, although data center 100 is shown with multiple pods, in some embodiments, the data center 100 may be embodied as a single pod. As described in more detail herein, each rack houses multiple sleds, each of which may be primarily equipped with a particular type of resource (e.g., memory devices, data storage devices, accelerator devices, general purpose processors), i.e., resources that can be logically coupled to form a composed node, which can act as, for example, a server. In the illustrative embodiment, the sleds in each pod 110, 120, 130, 140 are connected to multiple pod switches (e.g., switches that route data communications to and from sleds within the pod). The pod switches, in turn, connect with spine switches 150 that switch communications among pods (e.g., the pods 110, 120, 130, 140) in the data center 100. In some embodiments, the sleds may be connected with a fabric using Intel Omni-Path technology. In other embodiments, the sleds may be connected with other fabrics, such as InfiniBand or Ethernet. As described in more detail herein, resources within sleds in the data center 100 may be allocated to a group (referred to herein as a “managed node”) containing resources from one or more sleds to be collectively utilized in the execution of a workload. The workload can execute as if the resources belonging to the managed node were located on the same sled. The resources in a managed node may belong to sleds belonging to different racks, and even to different pods 110, 120, 130, 140. As such, some resources of a single sled may be allocated to one managed node while other resources of the same sled are allocated to a different managed node (e.g., one processor assigned to one managed node and another processor of the same sled assigned to a different managed node).

A data center comprising disaggregated resources, such as data center 100, can be used in a wide variety of contexts, such as enterprise, government, cloud service provider, and communications service provider (e.g., Telco's), as well in a wide variety of sizes, from cloud service provider mega-data centers that consume over 100,000 sq. ft. to single- or multi-rack installations for use in base stations.

The disaggregation of resources to sleds comprised predominantly of a single type of resource (e.g., compute sleds comprising primarily compute resources, memory sleds containing primarily memory resources), and the selective allocation and deallocation of the disaggregated resources to form a managed node assigned to execute a workload improves the operation and resource usage of the data center 100 relative to typical data centers comprised of hyperconverged servers containing compute, memory, storage and perhaps additional resources in a single chassis. For example, because sleds predominantly contain resources of a particular type, resources of a given type can be upgraded independently of other resources. Additionally, because different resources types (processors, storage, accelerators, etc.) typically have different refresh rates, greater resource utilization and reduced total cost of ownership may be achieved. For example, a data center operator can upgrade the processors throughout their facility by only swapping out the compute sleds. In such a case, accelerator and storage resources may not be contemporaneously upgraded and, rather, may be allowed to continue operating until those resources are scheduled for their own refresh. Resource utilization may also increase. For example, if managed nodes are composed based on requirements of the workloads that will be running on them, resources within a node are more likely to be fully utilized. Such utilization may allow for more managed nodes to run in a data center with a given set of resources, or for a data center expected to run a given set of workloads, to be built using fewer resources.

Referring now to FIG. 2, the pod 110, in the illustrative embodiment, includes a set of rows 200, 210, 220, 230 of racks 240. Each rack 240 may house multiple sleds (e.g., sixteen sleds) and provide power and data connections to the housed sleds, as described in more detail herein. In the illustrative embodiment, the racks in each row 200, 210, 220, 230 are connected to multiple pod switches 250, 260. The pod switch 250 includes a set of ports 252 to which the sleds of the racks of the pod 110 are connected and another set of ports 254 that connect the pod 110 to the spine switches 150 to provide connectivity to other pods in the data center 100. Similarly, the pod switch 260 includes a set of ports 262 to which the sleds of the racks of the pod 110 are connected and a set of ports 264 that connect the pod 110 to the spine switches 150. As such, the use of the pair of switches 250, 260 provides an amount of redundancy to the pod 110. For example, if either of the switches 250, 260 fails, the sleds in the pod 110 may still maintain data communication with the remainder of the data center 100 (e.g., sleds of other pods) through the other switch 250, 260. Furthermore, in the illustrative embodiment, the switches 150, 250, 260 may be embodied as dual-mode optical switches, capable of routing both Ethernet protocol communications carrying Internet Protocol (IP) packets and communications according to a second, high-performance link-layer protocol (e.g., PCI Express) via optical signaling media of an optical fabric.

It should be appreciated that each of the other pods 120, 130, 140 (as well as any additional pods of the data center 100) may be similarly structured as, and have components similar to, the pod 110 shown in and described in regard to FIG. 2 (e.g., each pod may have rows of racks housing multiple sleds as described above). Additionally, while two pod switches 250, 260 are shown, it should be understood that in other embodiments, each pod 110, 120, 130, 140 may be connected to a different number of pod switches, providing even more failover capacity. Of course, in other embodiments, pods may be arranged differently than the rows-of-racks configuration shown in FIGS. 1-2. For example, a pod may be embodied as multiple sets of racks in which each set of racks is arranged radially, i.e., the racks are equidistant from a center switch.

Referring now to FIGS. 3-5, each illustrative rack 240 of the data center 100 includes two elongated support posts 302, 304, which are arranged vertically. For example, the elongated support posts 302, 304 may extend upwardly from a floor of the data center 100 when deployed. The rack 240 also includes one or more horizontal pairs 310 of elongated support arms 312 (identified in FIG. 3 via a dashed ellipse) configured to support a sled of the data center 100 as discussed below. One elongated support arm 312 of the pair of elongated support arms 312 extends outwardly from the elongated support post 302 and the other elongated support arm 312 extends outwardly from the elongated support post 304.

In the illustrative embodiments, each sled of the data center 100 is embodied as a chassis-less sled. That is, each sled has a chassis-less circuit board substrate on which physical resources (e.g., processors, memory, accelerators, storage, etc.) are mounted as discussed in more detail below. As such, the rack 240 is configured to receive the chassis-less sleds. For example, each pair 310 of elongated support arms 312 defines a sled slot 320 of the rack 240, which is configured to receive a corresponding chassis-less sled. To do so, each illustrative elongated support arm 312 includes a circuit board guide 330 configured to receive the chassis-less circuit board substrate of the sled. Each circuit board guide 330 is secured to, or otherwise mounted to, a top side 332 of the corresponding elongated support arm 312. For example, in the illustrative embodiment, each circuit board guide 330 is mounted at a distal end of the corresponding elongated support arm 312 relative to the corresponding elongated support post 302, 304. For clarity of the Figures, not every circuit board guide 330 may be referenced in each Figure.

Each circuit board guide 330 includes an inner wall that defines a circuit board slot 380 configured to receive the chassis-less circuit board substrate of a sled 400 when the sled 400 is received in the corresponding sled slot 320 of the rack 240. To do so, as shown in FIG. 4, a user (or robot) aligns the chassis-less circuit board substrate of an illustrative chassis-less sled 400 to a sled slot 320. The user, or robot, may then slide the chassis-less circuit board substrate forward into the sled slot 320 such that each side edge 414 of the chassis-less circuit board substrate is received in a corresponding circuit board slot 380 of the circuit board guides 330 of the pair 310 of elongated support arms 312 that define the corresponding sled slot 320 as shown in FIG. 4. By having robotically accessible and robotically manipulable sleds comprising disaggregated resources, each type of resource can be upgraded independently of each other and at their own optimized refresh rate. Furthermore, the sleds are configured to blindly mate with power and data communication cables in each rack 240, enhancing their ability to be quickly removed, upgraded, reinstalled, and/or replaced. As such, in some embodiments, the data center 100 may operate (e.g., execute workloads, undergo maintenance and/or upgrades, etc.) without human involvement on the data center floor. In other embodiments, a human may facilitate one or more maintenance or upgrade operations in the data center 100.

It should be appreciated that each circuit board guide 330 is dual sided. That is, each circuit board guide 330 includes an inner wall that defines a circuit board slot 380 on each side of the circuit board guide 330. In this way, each circuit board guide 330 can support a chassis-less circuit board substrate on either side. As such, a single additional elongated support post may be added to the rack 240 to turn the rack 240 into a two-rack solution that can hold twice as many sled slots 320 as shown in FIG. 3. The illustrative rack 240 includes seven pairs 310 of elongated support arms 312 that define a corresponding seven sled slots 320, each configured to receive and support a corresponding sled 400 as discussed above. Of course, in other embodiments, the rack 240 may include additional or fewer pairs 310 of elongated support arms 312 (i.e., additional or fewer sled slots 320). It should be appreciated that because the sled 400 is chassis-less, the sled 400 may have an overall height that is different than typical servers. As such, in some embodiments, the height of each sled slot 320 may be shorter than the height of a typical server (e.g., shorter than a single rank unit, “1U”). That is, the vertical distance between each pair 310 of elongated support arms 312 may be less than a standard rack unit “1U.” Additionally, due to the relative decrease in height of the sled slots 320, the overall height of the rack 240 in some embodiments may be shorter than the height of traditional rack enclosures. For example, in some embodiments, each of the elongated support posts 302, 304 may have a length of six feet or less. Again, in other embodiments, the rack 240 may have different dimensions. For example, in some embodiments, the vertical distance between each pair 310 of elongated support arms 312 may be greater than a standard rack until “1U”. In such embodiments, the increased vertical distance between the sleds allows for larger heat sinks to be attached to the physical resources and for larger fans to be used (e.g., in the fan array 370 described below) for cooling each sled, which in turn can allow the physical resources to operate at increased power levels. Further, it should be appreciated that the rack 240 does not include any walls, enclosures, or the like. Rather, the rack 240 is an enclosure-less rack that is opened to the local environment. Of course, in some cases, an end plate may be attached to one of the elongated support posts 302, 304 in those situations in which the rack 240 forms an end-of-row rack in the data center 100.

In some embodiments, various interconnects may be routed upwardly or downwardly through the elongated support posts 302, 304. To facilitate such routing, each elongated support post 302, 304 includes an inner wall that defines an inner chamber in which interconnects may be located. The interconnects routed through the elongated support posts 302, 304 may be embodied as any type of interconnects including, but not limited to, data or communication interconnects to provide communication connections to each sled slot 320, power interconnects to provide power to each sled slot 320, and/or other types of interconnects.

The rack 240, in the illustrative embodiment, includes a support platform on which a corresponding optical data connector (not shown) is mounted. Each optical data connector is associated with a corresponding sled slot 320 and is configured to mate with an optical data connector of a corresponding sled 400 when the sled 400 is received in the corresponding sled slot 320. In some embodiments, optical connections between components (e.g., sleds, racks, and switches) in the data center 100 are made with a blind mate optical connection. For example, a door on each cable may prevent dust from contaminating the fiber inside the cable. In the process of connecting to a blind mate optical connector mechanism, the door is pushed open when the end of the cable approaches or enters the connector mechanism. Subsequently, the optical fiber inside the cable may enter a gel within the connector mechanism and the optical fiber of one cable comes into contact with the optical fiber of another cable within the gel inside the connector mechanism.

The illustrative rack 240 also includes a fan array 370 coupled to the cross-support arms of the rack 240. The fan array 370 includes one or more rows of cooling fans 372, which are aligned in a horizontal line between the elongated support posts 302, 304. In the illustrative embodiment, the fan array 370 includes a row of cooling fans 372 for each sled slot 320 of the rack 240. As discussed above, each sled 400 does not include any on-board cooling system in the illustrative embodiment and, as such, the fan array 370 provides cooling for each sled 400 received in the rack 240. Each rack 240, in the illustrative embodiment, also includes a power supply associated with each sled slot 320. Each power supply is secured to one of the elongated support arms 312 of the pair 310 of elongated support arms 312 that define the corresponding sled slot 320. For example, the rack 240 may include a power supply coupled or secured to each elongated support arm 312 extending from the elongated support post 302. Each power supply includes a power connector configured to mate with a power connector of the sled 400 when the sled 400 is received in the corresponding sled slot 320. In the illustrative embodiment, the sled 400 does not include any on-board power supply and, as such, the power supplies provided in the rack 240 supply power to corresponding sleds 400 when mounted to the rack 240. Each power supply is configured to satisfy the power requirements for its associated sled, which can vary from sled to sled. Additionally, the power supplies provided in the rack 240 can operate independent of each other. That is, within a single rack, a first power supply providing power to a compute sled can provide power levels that are different than power levels supplied by a second power supply providing power to an accelerator sled. The power supplies may be controllable at the sled level or rack level, and may be controlled locally by components on the associated sled or remotely, such as by another sled or an orchestrator.

Referring now to FIG. 6, the sled 400, in the illustrative embodiment, is configured to be mounted in a corresponding rack 240 of the data center 100 as discussed above. In some embodiments, each sled 400 may be optimized or otherwise configured for performing particular tasks, such as compute tasks, acceleration tasks, data storage tasks, etc. For example, the sled 400 may be embodied as a compute sled 800 as discussed below in regard to FIGS. 8-9, an accelerator sled 1000 as discussed below in regard to FIGS. 10-11, a storage sled 1200 as discussed below in regard to FIGS. 12-13, or as a sled optimized or otherwise configured to perform other specialized tasks, such as a memory sled 1400, discussed below in regard to FIG. 14.

As discussed above, the illustrative sled 400 includes a chassis-less circuit board substrate 602, which supports various physical resources (e.g., electrical components) mounted thereon. It should be appreciated that the circuit board substrate 602 is “chassis-less” in that the sled 400 does not include a housing or enclosure. Rather, the chassis-less circuit board substrate 602 is open to the local environment. The chassis-less circuit board substrate 602 may be formed from any material capable of supporting the various electrical components mounted thereon. For example, in an illustrative embodiment, the chassis-less circuit board substrate 602 is formed from an FR-4 glass-reinforced epoxy laminate material. Of course, other materials may be used to form the chassis-less circuit board substrate 602 in other embodiments.

As discussed in more detail below, the chassis-less circuit board substrate 602 includes multiple features that improve the thermal cooling characteristics of the various electrical components mounted on the chassis-less circuit board substrate 602. As discussed, the chassis-less circuit board substrate 602 does not include a housing or enclosure, which may improve the airflow over the electrical components of the sled 400 by reducing those structures that may inhibit air flow. For example, because the chassis-less circuit board substrate 602 is not positioned in an individual housing or enclosure, there is no vertically-arranged backplane (e.g., a backplate of the chassis) attached to the chassis-less circuit board substrate 602, which could inhibit air flow across the electrical components. Additionally, the chassis-less circuit board substrate 602 has a geometric shape configured to reduce the length of the airflow path across the electrical components mounted to the chassis-less circuit board substrate 602. For example, the illustrative chassis-less circuit board substrate 602 has a width 604 that is greater than a depth 606 of the chassis-less circuit board substrate 602. In one particular embodiment, for example, the chassis-less circuit board substrate 602 has a width of about 21 inches and a depth of about 9 inches, compared to a typical server that has a width of about 17 inches and a depth of about 39 inches. As such, an airflow path 608 that extends from a front edge 610 of the chassis-less circuit board substrate 602 toward a rear edge 612 has a shorter distance relative to typical servers, which may improve the thermal cooling characteristics of the sled 400. Furthermore, although not illustrated in FIG. 6, the various physical resources mounted to the chassis-less circuit board substrate 602 are mounted in corresponding locations such that no two substantively heat-producing electrical components shadow each other as discussed in more detail below. That is, no two electrical components, which produce appreciable heat during operation (i.e., greater than a nominal heat sufficient enough to adversely impact the cooling of another electrical component), are mounted to the chassis-less circuit board substrate 602 linearly in-line with each other along the direction of the airflow path 608 (i.e., along a direction extending from the front edge 610 toward the rear edge 612 of the chassis-less circuit board substrate 602).

As discussed above, the illustrative sled 400 includes one or more physical resources 620 mounted to a top side 650 of the chassis-less circuit board substrate 602. Although two physical resources 620 are shown in FIG. 6, it should be appreciated that the sled 400 may include one, two, or more physical resources 620 in other embodiments. The physical resources 620 may be embodied as any type of processor, controller, or other compute circuit capable of performing various tasks such as compute functions and/or controlling the functions of the sled 400 depending on, for example, the type or intended functionality of the sled 400. For example, as discussed in more detail below, the physical resources 620 may be embodied as high-performance processors in embodiments in which the sled 400 is embodied as a compute sled, as accelerator co-processors or circuits in embodiments in which the sled 400 is embodied as an accelerator sled, storage controllers in embodiments in which the sled 400 is embodied as a storage sled, or a set of memory devices in embodiments in which the sled 400 is embodied as a memory sled.

The sled 400 also includes one or more additional physical resources 630 mounted to the top side 650 of the chassis-less circuit board substrate 602. In the illustrative embodiment, the additional physical resources include a network interface controller (NIC) as discussed in more detail below. Of course, depending on the type and functionality of the sled 400, the physical resources 630 may include additional or other electrical components, circuits, and/or devices in other embodiments.

The physical resources 620 are communicatively coupled to the physical resources 630 via an input/output (I/O) subsystem 622. The I/O subsystem 622 may be embodied as circuitry and/or components to facilitate input/output operations with the physical resources 620, the physical resources 630, and/or other components of the sled 400. For example, the I/O subsystem 622 may be embodied as, or otherwise include, memory controller hubs, input/output control hubs, integrated sensor hubs, firmware devices, communication links (e.g., point-to-point links, bus links, wires, cables, waveguides, light guides, printed circuit board traces, etc.), and/or other components and subsystems to facilitate the input/output operations. In the illustrative embodiment, the I/O subsystem 622 is embodied as, or otherwise includes, a double data rate 4 (DDR4) data bus or a DDR5 data bus, as described further below.

In some embodiments, the sled 400 may also include a resource-to-resource interconnect 624. The resource-to-resource interconnect 624 may be embodied as any type of communication interconnect capable of facilitating resource-to-resource communications. In the illustrative embodiment, the resource-to-resource interconnect 624 is embodied as a high-speed point-to-point interconnect (e.g., faster than the I/O subsystem 622). For example, the resource-to-resource interconnect 624 may be embodied as a QuickPath Interconnect (QPI), an UltraPath Interconnect (UPI), or other high-speed point-to-point interconnect dedicated to resource-to-resource communications.

The sled 400 also includes a power connector 640 configured to mate with a corresponding power connector of the rack 240 when the sled 400 is mounted in the corresponding rack 240. The sled 400 receives power from a power supply of the rack 240 via the power connector 640 to supply power to the various electrical components of the sled 400. That is, the sled 400 does not include any local power supply (i.e., an on-board power supply) to provide power to the electrical components of the sled 400. The exclusion of a local or on-board power supply facilitates the reduction in the overall footprint of the chassis-less circuit board substrate 602, which may increase the thermal cooling characteristics of the various electrical components mounted on the chassis-less circuit board substrate 602 as discussed above. In some embodiments, voltage regulators are placed on a bottom side 750 (see FIG. 7) of the chassis-less circuit board substrate 602 directly opposite of the processors 820 (see FIG. 8), and power is routed from the voltage regulators to the processors 820 by vias extending through the circuit board substrate 602. Such a configuration provides an increased thermal budget, additional current and/or voltage, and better voltage control relative to typical printed circuit boards in which processor power is delivered from a voltage regulator, in part, by printed circuit traces.

In some embodiments, the sled 400 may also include mounting features 642 configured to mate with a mounting arm, or other structure, of a robot to facilitate the placement of the sled 600 in a rack 240 by the robot. The mounting features 642 may be embodied as any type of physical structures that allow the robot to grasp the sled 400 without damaging the chassis-less circuit board substrate 602 or the electrical components mounted thereto. For example, in some embodiments, the mounting features 642 may be embodied as non-conductive pads attached to the chassis-less circuit board substrate 602. In other embodiments, the mounting features may be embodied as brackets, braces, or other similar structures attached to the chassis-less circuit board substrate 602. The particular number, shape, size, and/or make-up of the mounting feature 642 may depend on the design of the robot configured to manage the sled 400.

Referring now to FIG. 7, in addition to the physical resources 630 mounted on the top side 650 of the chassis-less circuit board substrate 602, the sled 400 also includes one or more memory devices 720 mounted to a bottom side 750 of the chassis-less circuit board substrate 602. That is, the chassis-less circuit board substrate 602 is embodied as a double-sided circuit board. The physical resources 620 are communicatively coupled to the memory devices 720 via the I/O subsystem 622. For example, the physical resources 620 and the memory devices 720 may be communicatively coupled by one or more vias extending through the chassis-less circuit board substrate 602. Each physical resource 620 may be communicatively coupled to a different set of one or more memory devices 720 in some embodiments. Alternatively, in other embodiments, each physical resource 620 may be communicatively coupled to each memory device 720.

The memory devices 720 may be embodied as any type of memory device capable of storing data for the physical resources 620 during operation of the sled 400, such as any type of volatile (e.g., dynamic random access memory (DRAM), etc.) or non-volatile memory. Volatile memory may be a memory that requires power to maintain the state of data stored by the medium. Non-limiting examples of volatile memory may include various types of random access memory (RAM), such as dynamic random access memory (DRAM) or static random access memory (SRAM). One particular type of DRAM that may be used in a memory module is synchronous dynamic random access memory (SDRAM). In particular embodiments, DRAM of a memory component may comply with a standard promulgated by the Joint Electronic Device Engineering Council (JEDEC), such as JESD79F for DDR SDRAM, JESD79-2F for DDR2 SDRAM, JESD79-3F for DDR3 SDRAM, JESD79-4A for DDR4 SDRAM, JESD209 for Low Power DDR (LPDDR), JESD209-2 for LPDDR2, JESD209-3 for LPDDR3, and JESD209-4 for LPDDR4. Such standards (and similar standards) may be referred to as DDR-based standards and communication interfaces of the memory devices that implement such standards may be referred to as DDR-based interfaces.

In one embodiment, the memory device is a block addressable memory device, such as those based on NAND or NOR technologies, such as multi-threshold level NAND flash memory or NOR flash memory. A memory device may also include byte-addressable write-in-place nonvolatile memory devices, such as Intel 3D XPoint™ memory, Micron QuantX™ memory, magnetoresistive random access memory (MRAM) memory that incorporates memristor technology, or other byte addressable write-in-place nonvolatile memory devices. In some embodiments, the memory device may comprise a transistor-less stackable cross point architecture in which memory cells sit at the intersection of word lines and bit lines and are individually addressable and in which bit storage is based on a change in bulk resistance. In one embodiment, the memory device may be or may include memory devices that use chalcogenide glass, single or multi-level Phase Change Memory (PCM), a resistive memory, nanowire memory, ferroelectric transistor random access memory (FeTRAM), anti-ferroelectric memory, magnetoresistive random access memory (MRAM) memory that incorporates memristor technology, resistive memory including the metal oxide base, the oxygen vacancy base and the conductive bridge Random Access Memory (CB-RAM), or spin transfer torque (STT)-MRAM, a spintronic magnetic junction memory based device, a magnetic tunneling junction (MTJ) based device, a DW (Domain Wall) and SOT (Spin Orbit Transfer) based device, a thyristor based memory device, or a combination of any of the above, or other memory. The memory device may refer to the die itself and/or to a packaged memory product.

Referring now to FIG. 8, in some embodiments, the sled 400 may be embodied as a compute sled 800. The compute sled 800 is optimized, or otherwise configured, to perform compute tasks. Of course, as discussed above, the compute sled 800 may rely on other sleds, such as acceleration sleds and/or storage sleds, to perform such compute tasks. The compute sled 800 includes various physical resources (e.g., electrical components) similar to the physical resources of the sled 400, which have been identified in FIG. 8 using the same reference numbers. The description of such components provided above in regard to FIGS. 6 and 7 applies to the corresponding components of the compute sled 800 and is not repeated herein for clarity of the description of the compute sled 800.

In the illustrative compute sled 800, the physical resources 620 are embodied as processors 820. Although only two processors 820 are shown in FIG. 8, it should be appreciated that the compute sled 800 may include additional processors 820 in other embodiments. Illustratively, the processors 820 are embodied as high-performance processors 820 and may be configured to operate at a relatively high power rating. Although the processors 820 generate additional heat operating at power ratings greater than typical processors (which operate at around 155-230 W), the enhanced thermal cooling characteristics of the chassis-less circuit board substrate 602 discussed above facilitate the higher power operation. For example, in the illustrative embodiment, the processors 820 are configured to operate at a power rating of at least 250 W. In some embodiments, the processors 820 may be configured to operate at a power rating of at least 350 W.

In some embodiments, the compute sled 800 may also include a processor-to-processor interconnect 842. Similar to the resource-to-resource interconnect 624 of the sled 400 discussed above, the processor-to-processor interconnect 842 may be embodied as any type of communication interconnect capable of facilitating processor-to-processor interconnect 842 communications. In the illustrative embodiment, the processor-to-processor interconnect 842 is embodied as a high-speed point-to-point interconnect (e.g., faster than the I/O subsystem 622). For example, the processor-to-processor interconnect 842 may be embodied as a QuickPath Interconnect (QPI), an UltraPath Interconnect (UPI), or other high-speed point-to-point interconnect dedicated to processor-to-processor communications.

The compute sled 800 also includes a communication circuit 830. The illustrative communication circuit 830 includes a network interface controller (NIC) 832, which may also be referred to as a host fabric interface (HFI). The NIC 832 may be embodied as, or otherwise include, any type of integrated circuit, discrete circuits, controller chips, chipsets, add-in-boards, daughtercards, network interface cards, or other devices that may be used by the compute sled 800 to connect with another compute device (e.g., with other sleds 400). In some embodiments, the NIC 832 may be embodied as part of a system-on-a-chip (SoC) that includes one or more processors, or included on a multichip package that also contains one or more processors. In some embodiments, the NIC 832 may include a local processor (not shown) and/or a local memory (not shown) that are both local to the NIC 832. In such embodiments, the local processor of the NIC 832 may be capable of performing one or more of the functions of the processors 820. Additionally or alternatively, in such embodiments, the local memory of the NIC 832 may be integrated into one or more components of the compute sled at the board level, socket level, chip level, and/or other levels.

The communication circuit 830 is communicatively coupled to an optical data connector 834. The optical data connector 834 is configured to mate with a corresponding optical data connector of the rack 240 when the compute sled 800 is mounted in the rack 240. Illustratively, the optical data connector 834 includes a plurality of optical fibers which lead from a mating surface of the optical data connector 834 to an optical transceiver 836. The optical transceiver 836 is configured to convert incoming optical signals from the rack-side optical data connector to electrical signals and to convert electrical signals to outgoing optical signals to the rack-side optical data connector. Although shown as forming part of the optical data connector 834 in the illustrative embodiment, the optical transceiver 836 may form a portion of the communication circuit 830 in other embodiments.

In some embodiments, the compute sled 800 may also include an expansion connector 840. In such embodiments, the expansion connector 840 is configured to mate with a corresponding connector of an expansion chassis-less circuit board substrate to provide additional physical resources to the compute sled 800. The additional physical resources may be used, for example, by the processors 820 during operation of the compute sled 800. The expansion chassis-less circuit board substrate may be substantially similar to the chassis-less circuit board substrate 602 discussed above and may include various electrical components mounted thereto. The particular electrical components mounted to the expansion chassis-less circuit board substrate may depend on the intended functionality of the expansion chassis-less circuit board substrate. For example, the expansion chassis-less circuit board substrate may provide additional compute resources, memory resources, and/or storage resources. As such, the additional physical resources of the expansion chassis-less circuit board substrate may include, but is not limited to, processors, memory devices, storage devices, and/or accelerator circuits including, for example, field programmable gate arrays (FPGA), application-specific integrated circuits (ASICs), security co-processors, graphics processing units (GPUs), machine learning circuits, or other specialized processors, controllers, devices, and/or circuits.

Referring now to FIG. 9, an illustrative embodiment of the compute sled 800 is shown. As shown, the processors 820, communication circuit 830, and optical data connector 834 are mounted to the top side 650 of the chassis-less circuit board substrate 602. Any suitable attachment or mounting technology may be used to mount the physical resources of the compute sled 800 to the chassis-less circuit board substrate 602. For example, the various physical resources may be mounted in corresponding sockets (e.g., a processor socket), holders, or brackets. In some cases, some of the electrical components may be directly mounted to the chassis-less circuit board substrate 602 via soldering or similar techniques.

As discussed above, the individual processors 820 and communication circuit 830 are mounted to the top side 650 of the chassis-less circuit board substrate 602 such that no two heat-producing, electrical components shadow each other. In the illustrative embodiment, the processors 820 and communication circuit 830 are mounted in corresponding locations on the top side 650 of the chassis-less circuit board substrate 602 such that no two of those physical resources are linearly in-line with others along the direction of the airflow path 608. It should be appreciated that, although the optical data connector 834 is in-line with the communication circuit 830, the optical data connector 834 produces no or nominal heat during operation.

The memory devices 720 of the compute sled 800 are mounted to the bottom side 750 of the of the chassis-less circuit board substrate 602 as discussed above in regard to the sled 400. Although mounted to the bottom side 750, the memory devices 720 are communicatively coupled to the processors 820 located on the top side 650 via the I/O subsystem 622. Because the chassis-less circuit board substrate 602 is embodied as a double-sided circuit board, the memory devices 720 and the processors 820 may be communicatively coupled by one or more vias, connectors, or other mechanisms extending through the chassis-less circuit board substrate 602. Of course, each processor 820 may be communicatively coupled to a different set of one or more memory devices 720 in some embodiments. Alternatively, in other embodiments, each processor 820 may be communicatively coupled to each memory device 720. In some embodiments, the memory devices 720 may be mounted to one or more memory mezzanines on the bottom side of the chassis-less circuit board substrate 602 and may interconnect with a corresponding processor 820 through a ball-grid array.

Each of the processors 820 includes a heat sink 850 secured thereto. Due to the mounting of the memory devices 720 to the bottom side 750 of the chassis-less circuit board substrate 602 (as well as the vertical spacing of the sleds 400 in the corresponding rack 240), the top side 650 of the chassis-less circuit board substrate 602 includes additional “free” area or space that facilitates the use of heat sinks 850 having a larger size relative to traditional heat sinks used in typical servers. Additionally, due to the improved thermal cooling characteristics of the chassis-less circuit board substrate 602, none of the processor heat sinks 850 include cooling fans attached thereto. That is, each of the heat sinks 850 is embodied as a fan-less heat sink. In some embodiments, the heat sinks 850 mounted atop the processors 820 may overlap with the heat sink attached to the communication circuit 830 in the direction of the airflow path 608 due to their increased size, as illustratively suggested by FIG. 9.

Referring now to FIG. 10, in some embodiments, the sled 400 may be embodied as an accelerator sled 1000. The accelerator sled 1000 is configured, to perform specialized compute tasks, such as machine learning, encryption, hashing, or other computational-intensive task. In some embodiments, for example, a compute sled 800 may offload tasks to the accelerator sled 1000 during operation. The accelerator sled 1000 includes various components similar to components of the sled 400 and/or compute sled 800, which have been identified in FIG. 10 using the same reference numbers. The description of such components provided above in regard to FIGS. 6, 7, and 8 apply to the corresponding components of the accelerator sled 1000 and is not repeated herein for clarity of the description of the accelerator sled 1000.

In the illustrative accelerator sled 1000, the physical resources 620 are embodied as accelerator circuits 1020. Although only two accelerator circuits 1020 are shown in FIG. 10, it should be appreciated that the accelerator sled 1000 may include additional accelerator circuits 1020 in other embodiments. For example, as shown in FIG. 11, the accelerator sled 1000 may include four accelerator circuits 1020 in some embodiments. The accelerator circuits 1020 may be embodied as any type of processor, co-processor, compute circuit, or other device capable of performing compute or processing operations. For example, the accelerator circuits 1020 may be embodied as, for example, field programmable gate arrays (FPGA), application-specific integrated circuits (ASICs), security co-processors, graphics processing units (GPUs), neuromorphic processor units, quantum computers, machine learning circuits, or other specialized processors, controllers, devices, and/or circuits.

In some embodiments, the accelerator sled 1000 may also include an accelerator-to-accelerator interconnect 1042. Similar to the resource-to-resource interconnect 624 of the sled 600 discussed above, the accelerator-to-accelerator interconnect 1042 may be embodied as any type of communication interconnect capable of facilitating accelerator-to-accelerator communications. In the illustrative embodiment, the accelerator-to-accelerator interconnect 1042 is embodied as a high-speed point-to-point interconnect (e.g., faster than the I/O subsystem 622). For example, the accelerator-to-accelerator interconnect 1042 may be embodied as a QuickPath Interconnect (QPI), an UltraPath Interconnect (UPI), or other high-speed point-to-point interconnect dedicated to processor-to-processor communications. In some embodiments, the accelerator circuits 1020 may be daisy-chained with a primary accelerator circuit 1020 connected to the NIC 832 and memory 720 through the I/O subsystem 622 and a secondary accelerator circuit 1020 connected to the NIC 832 and memory 720 through a primary accelerator circuit 1020.

Referring now to FIG. 11, an illustrative embodiment of the accelerator sled 1000 is shown. As discussed above, the accelerator circuits 1020, communication circuit 830, and optical data connector 834 are mounted to the top side 650 of the chassis-less circuit board substrate 602. Again, the individual accelerator circuits 1020 and communication circuit 830 are mounted to the top side 650 of the chassis-less circuit board substrate 602 such that no two heat-producing, electrical components shadow each other as discussed above. The memory devices 720 of the accelerator sled 1000 are mounted to the bottom side 750 of the of the chassis-less circuit board substrate 602 as discussed above in regard to the sled 600. Although mounted to the bottom side 750, the memory devices 720 are communicatively coupled to the accelerator circuits 1020 located on the top side 650 via the I/O subsystem 622 (e.g., through vias). Further, each of the accelerator circuits 1020 may include a heat sink 1070 that is larger than a traditional heat sink used in a server. As discussed above with reference to the heat sinks 870, the heat sinks 1070 may be larger than traditional heat sinks because of the “free” area provided by the memory resources 720 being located on the bottom side 750 of the chassis-less circuit board substrate 602 rather than on the top side 650.

Referring now to FIG. 12, in some embodiments, the sled 400 may be embodied as a storage sled 1200. The storage sled 1200 is configured, to store data in a data storage 1250 local to the storage sled 1200. For example, during operation, a compute sled 800 or an accelerator sled 1000 may store and retrieve data from the data storage 1250 of the storage sled 1200. The storage sled 1200 includes various components similar to components of the sled 400 and/or the compute sled 800, which have been identified in FIG. 12 using the same reference numbers. The description of such components provided above in regard to FIGS. 6, 7, and 8 apply to the corresponding components of the storage sled 1200 and is not repeated herein for clarity of the description of the storage sled 1200.

In the illustrative storage sled 1200, the physical resources 620 are embodied as storage controllers 1220. Although only two storage controllers 1220 are shown in FIG. 12, it should be appreciated that the storage sled 1200 may include additional storage controllers 1220 in other embodiments. The storage controllers 1220 may be embodied as any type of processor, controller, or control circuit capable of controlling the storage and retrieval of data into the data storage 1250 based on requests received via the communication circuit 830. In the illustrative embodiment, the storage controllers 1220 are embodied as relatively low-power processors or controllers. For example, in some embodiments, the storage controllers 1220 may be configured to operate at a power rating of about 75 watts.

In some embodiments, the storage sled 1200 may also include a controller-to-controller interconnect 1242. Similar to the resource-to-resource interconnect 624 of the sled 400 discussed above, the controller-to-controller interconnect 1242 may be embodied as any type of communication interconnect capable of facilitating controller-to-controller communications. In the illustrative embodiment, the controller-to-controller interconnect 1242 is embodied as a high-speed point-to-point interconnect (e.g., faster than the I/O subsystem 622). For example, the controller-to-controller interconnect 1242 may be embodied as a QuickPath Interconnect (QPI), an UltraPath Interconnect (UPI), or other high-speed point-to-point interconnect dedicated to processor-to-processor communications.

Referring now to FIG. 13, an illustrative embodiment of the storage sled 1200 is shown. In the illustrative embodiment, the data storage 1250 is embodied as, or otherwise includes, a storage cage 1252 configured to house one or more solid state drives (SSDs) 1254. To do so, the storage cage 1252 includes a number of mounting slots 1256, each of which is configured to receive a corresponding solid state drive 1254. Each of the mounting slots 1256 includes a number of drive guides 1258 that cooperate to define an access opening 1260 of the corresponding mounting slot 1256. The storage cage 1252 is secured to the chassis-less circuit board substrate 602 such that the access openings face away from (i.e., toward the front of) the chassis-less circuit board substrate 602. As such, solid state drives 1254 are accessible while the storage sled 1200 is mounted in a corresponding rack 204. For example, a solid state drive 1254 may be swapped out of a rack 240 (e.g., via a robot) while the storage sled 1200 remains mounted in the corresponding rack 240.

The storage cage 1252 illustratively includes sixteen mounting slots 1256 and is capable of mounting and storing sixteen solid state drives 1254. Of course, the storage cage 1252 may be configured to store additional or fewer solid state drives 1254 in other embodiments. Additionally, in the illustrative embodiment, the solid state drivers are mounted vertically in the storage cage 1252, but may be mounted in the storage cage 1252 in a different orientation in other embodiments. Each solid state drive 1254 may be embodied as any type of data storage device capable of storing long term data. To do so, the solid state drives 1254 may include volatile and non-volatile memory devices discussed above.

As shown in FIG. 13, the storage controllers 1220, the communication circuit 830, and the optical data connector 834 are illustratively mounted to the top side 650 of the chassis-less circuit board substrate 602. Again, as discussed above, any suitable attachment or mounting technology may be used to mount the electrical components of the storage sled 1200 to the chassis-less circuit board substrate 602 including, for example, sockets (e.g., a processor socket), holders, brackets, soldered connections, and/or other mounting or securing techniques.

As discussed above, the individual storage controllers 1220 and the communication circuit 830 are mounted to the top side 650 of the chassis-less circuit board substrate 602 such that no two heat-producing, electrical components shadow each other. For example, the storage controllers 1220 and the communication circuit 830 are mounted in corresponding locations on the top side 650 of the chassis-less circuit board substrate 602 such that no two of those electrical components are linearly in-line with each other along the direction of the airflow path 608.

The memory devices 720 of the storage sled 1200 are mounted to the bottom side 750 of the of the chassis-less circuit board substrate 602 as discussed above in regard to the sled 400. Although mounted to the bottom side 750, the memory devices 720 are communicatively coupled to the storage controllers 1220 located on the top side 650 via the I/O subsystem 622. Again, because the chassis-less circuit board substrate 602 is embodied as a double-sided circuit board, the memory devices 720 and the storage controllers 1220 may be communicatively coupled by one or more vias, connectors, or other mechanisms extending through the chassis-less circuit board substrate 602. Each of the storage controllers 1220 includes a heat sink 1270 secured thereto. As discussed above, due to the improved thermal cooling characteristics of the chassis-less circuit board substrate 602 of the storage sled 1200, none of the heat sinks 1270 include cooling fans attached thereto. That is, each of the heat sinks 1270 is embodied as a fan-less heat sink.

Referring now to FIG. 14, in some embodiments, the sled 400 may be embodied as a memory sled 1400. The memory sled 1400 is optimized, or otherwise configured, to provide other sleds 400 (e.g., compute sleds 800, accelerator sleds 1000, etc.) with access to a pool of memory (e.g., in two or more sets 1430, 1432 of memory devices 720) local to the memory sled 1200. For example, during operation, a compute sled 800 or an accelerator sled 1000 may remotely write to and/or read from one or more of the memory sets 1430, 1432 of the memory sled 1200 using a logical address space that maps to physical addresses in the memory sets 1430, 1432. The memory sled 1400 includes various components similar to components of the sled 400 and/or the compute sled 800, which have been identified in FIG. 14 using the same reference numbers. The description of such components provided above in regard to FIGS. 6, 7, and 8 apply to the corresponding components of the memory sled 1400 and is not repeated herein for clarity of the description of the memory sled 1400.

In the illustrative memory sled 1400, the physical resources 620 are embodied as memory controllers 1420. Although only two memory controllers 1420 are shown in FIG. 14, it should be appreciated that the memory sled 1400 may include additional memory controllers 1420 in other embodiments. The memory controllers 1420 may be embodied as any type of processor, controller, or control circuit capable of controlling the writing and reading of data into the memory sets 1430, 1432 based on requests received via the communication circuit 830. In the illustrative embodiment, each memory controller 1420 is connected to a corresponding memory set 1430, 1432 to write to and read from memory devices 720 within the corresponding memory set 1430, 1432 and enforce any permissions (e.g., read, write, etc.) associated with sled 400 that has sent a request to the memory sled 1400 to perform a memory access operation (e.g., read or write).

In some embodiments, the memory sled 1400 may also include a controller-to-controller interconnect 1442. Similar to the resource-to-resource interconnect 624 of the sled 400 discussed above, the controller-to-controller interconnect 1442 may be embodied as any type of communication interconnect capable of facilitating controller-to-controller communications. In the illustrative embodiment, the controller-to-controller interconnect 1442 is embodied as a high-speed point-to-point interconnect (e.g., faster than the I/O subsystem 622). For example, the controller-to-controller interconnect 1442 may be embodied as a QuickPath Interconnect (QPI), an UltraPath Interconnect (UPI), or other high-speed point-to-point interconnect dedicated to processor-to-processor communications. As such, in some embodiments, a memory controller 1420 may access, through the controller-to-controller interconnect 1442, memory that is within the memory set 1432 associated with another memory controller 1420. In some embodiments, a scalable memory controller is made of multiple smaller memory controllers, referred to herein as “chiplets”, on a memory sled (e.g., the memory sled 1400). The chiplets may be interconnected (e.g., using EMIB (Embedded Multi-Die Interconnect Bridge)). The combined chiplet memory controller may scale up to a relatively large number of memory controllers and I/O ports, (e.g., up to 16 memory channels). In some embodiments, the memory controllers 1420 may implement a memory interleave (e.g., one memory address is mapped to the memory set 1430, the next memory address is mapped to the memory set 1432, and the third address is mapped to the memory set 1430, etc.). The interleaving may be managed within the memory controllers 1420, or from CPU sockets (e.g., of the compute sled 800) across network links to the memory sets 1430, 1432, and may improve the latency associated with performing memory access operations as compared to accessing contiguous memory addresses from the same memory device.

Further, in some embodiments, the memory sled 1400 may be connected to one or more other sleds 400 (e.g., in the same rack 240 or an adjacent rack 240) through a waveguide, using the waveguide connector 1480. In the illustrative embodiment, the waveguides are 64 millimeter waveguides that provide 16 Rx (i.e., receive) lanes and 16 Tx (i.e., transmit) lanes. Each lane, in the illustrative embodiment, is either 16 GHz or 32 GHz. In other embodiments, the frequencies may be different. Using a waveguide may provide high throughput access to the memory pool (e.g., the memory sets 1430, 1432) to another sled (e.g., a sled 400 in the same rack 240 or an adjacent rack 240 as the memory sled 1400) without adding to the load on the optical data connector 834.

Referring now to FIG. 15, a system for executing one or more workloads (e.g., applications) may be implemented in accordance with the data center 100. In the illustrative embodiment, the system 1510 includes an orchestrator server 1520, which may be embodied as a managed node comprising a compute device (e.g., a processor 820 on a compute sled 800) executing management software (e.g., a cloud operating environment, such as OpenStack) that is communicatively coupled to multiple sleds 400 including a large number of compute sleds 1530 (e.g., each similar to the compute sled 800), memory sleds 1540 (e.g., each similar to the memory sled 1400), accelerator sleds 1550 (e.g., each similar to the memory sled 1000), and storage sleds 1560 (e.g., each similar to the storage sled 1200). One or more of the sleds 1530, 1540, 1550, 1560 may be grouped into a managed node 1570, such as by the orchestrator server 1520, to collectively perform a workload (e.g., an application 1532 executed in a virtual machine or in a container). The managed node 1570 may be embodied as an assembly of physical resources 620, such as processors 820, memory resources 720, accelerator circuits 1020, or data storage 1250, from the same or different sleds 400. Further, the managed node may be established, defined, or “spun up” by the orchestrator server 1520 at the time a workload is to be assigned to the managed node or at any other time, and may exist regardless of whether any workloads are presently assigned to the managed node. In the illustrative embodiment, the orchestrator server 1520 may selectively allocate and/or deallocate physical resources 620 from the sleds 400 and/or add or remove one or more sleds 400 from the managed node 1570 as a function of quality of service (QoS) targets (e.g., a target throughput, a target latency, a target number instructions per second, etc.) associated with a service level agreement for the workload (e.g., the application 1532). In doing so, the orchestrator server 1520 may receive telemetry data indicative of performance conditions (e.g., throughput, latency, instructions per second, etc.) in each sled 400 of the managed node 1570 and compare the telemetry data to the quality of service targets to determine whether the quality of service targets are being satisfied. The orchestrator server 1520 may additionally determine whether one or more physical resources may be deallocated from the managed node 1570 while still satisfying the QoS targets, thereby freeing up those physical resources for use in another managed node (e.g., to execute a different workload). Alternatively, if the QoS targets are not presently satisfied, the orchestrator server 1520 may determine to dynamically allocate additional physical resources to assist in the execution of the workload (e.g., the application 1532) while the workload is executing. Similarly, the orchestrator server 1520 may determine to dynamically deallocate physical resources from a managed node if the orchestrator server 1520 determines that deallocating the physical resource would result in QoS targets still being met.

Additionally, in some embodiments, the orchestrator server 1520 may identify trends in the resource utilization of the workload (e.g., the application 1532), such as by identifying phases of execution (e.g., time periods in which different operations, each having different resource utilizations characteristics, are performed) of the workload (e.g., the application 1532) and pre-emptively identifying available resources in the data center 100 and allocating them to the managed node 1570 (e.g., within a predefined time period of the associated phase beginning). In some embodiments, the orchestrator server 1520 may model performance based on various latencies and a distribution scheme to place workloads among compute sleds and other resources (e.g., accelerator sleds, memory sleds, storage sleds) in the data center 100. For example, the orchestrator server 1520 may utilize a model that accounts for the performance of resources on the sleds 400 (e.g., FPGA performance, memory access latency, etc.) and the performance (e.g., congestion, latency, bandwidth) of the path through the network to the resource (e.g., FPGA). As such, the orchestrator server 1520 may determine which resource(s) should be used with which workloads based on the total latency associated with each potential resource available in the data center 100 (e.g., the latency associated with the performance of the resource itself in addition to the latency associated with the path through the network between the compute sled executing the workload and the sled 400 on which the resource is located).

In some embodiments, the orchestrator server 1520 may generate a map of heat generation in the data center 100 using telemetry data (e.g., temperatures, fan speeds, etc.) reported from the sleds 400 and allocate resources to managed nodes as a function of the map of heat generation and predicted heat generation associated with different workloads, to maintain a target temperature and heat distribution in the data center 100. Additionally or alternatively, in some embodiments, the orchestrator server 1520 may organize received telemetry data into a hierarchical model that is indicative of a relationship between the managed nodes (e.g., a spatial relationship such as the physical locations of the resources of the managed nodes within the data center 100 and/or a functional relationship, such as groupings of the managed nodes by the customers the managed nodes provide services for, the types of functions typically performed by the managed nodes, managed nodes that typically share or exchange workloads among each other, etc.). Based on differences in the physical locations and resources in the managed nodes, a given workload may exhibit different resource utilizations (e.g., cause a different internal temperature, use a different percentage of processor or memory capacity) across the resources of different managed nodes. The orchestrator server 1520 may determine the differences based on the telemetry data stored in the hierarchical model and factor the differences into a prediction of future resource utilization of a workload if the workload is reassigned from one managed node to another managed node, to accurately balance resource utilization in the data center 100. In some embodiments, the orchestrator server 1520 may identify patterns in resource utilization phases of the workloads and use the patterns to predict future resource utilization of the workloads.

To reduce the computational load on the orchestrator server 1520 and the data transfer load on the network, in some embodiments, the orchestrator server 1520 may send self-test information to the sleds 400 to enable each sled 400 to locally (e.g., on the sled 400) determine whether telemetry data generated by the sled 400 satisfies one or more conditions (e.g., an available capacity that satisfies a predefined threshold, a temperature that satisfies a predefined threshold, etc.). Each sled 400 may then report back a simplified result (e.g., yes or no) to the orchestrator server 1520, which the orchestrator server 1520 may utilize in determining the allocation of resources to managed nodes.

Referring now to FIG. 16, a disaggregated system 1600 for providing latency-aware consensus management includes a master controller 1602 which may be embodied as any compute device (e.g., a compute sled) capable managing the operations of multiple sleds across the system 1600 (e.g., across multiple pods) and configuring a software defined network (e.g., dynamically and programmatically configuring communication paths through a network and disassociating a data plane (e.g., data in packets sent through the network) from a control plane (e.g., routing of packets through the network)). The system 1600 additionally includes an orchestrator server 1604, similar to the orchestrator server 1520 described with reference to FIG. 15. Further, the system 1600 includes a monitor server 1606 which may collect telemetry data from sleds 1612, 1614, 1610, 1616 in the system 1600 and provide the telemetry data to other compute devices (e.g., to the orchestrator server 1604 and/or the master controller 1602). While shown as separate compute devices in FIG. 16, in some embodiments, one or more of the master controller 1602, the orchestrator server 1604, and the monitor server 1606 may be combined into a single unit.

The system 1600 includes one or more compute sleds 1610, each similar to the compute sled 800. The system 1600 also includes one or more accelerator sleds 1612, each similar to the accelerator sled 1000. Further, the system 1600 includes one or more storage sleds 1614, each similar to the storage sled 1200 and one or more memory sleds 1616, each similar to the memory sled 1400. The compute sled 1610, in the illustrative embodiment, includes a processor 1620, similar to the processor 820, which may be assigned to execute an application 1670 (e.g., a set of operations, also referred to herein as a workload) on behalf of a customer (e.g., a tenant). The accelerator sled 1612 includes a set of accelerator devices 1622, 1624, similar to the accelerator circuits 1020, each of which may be embodied as any device or circuitry (e.g., an FPGA, an ASIC, a GPU, reconfigurable circuitry, etc.) capable of executing a defined set of functions (e.g., a kernel) faster than a general purpose processor is capable of executing the functions. The storage sled 1614 includes a set of data storage devices 1626, 1628, each of which may be embodied as any device capable of storing data in nonvolatile memory (e.g., similar to the solid state drive 1254). In addition, the memory sled 1616 includes a set of memory devices 1630, 1632 similar to the memory resources 720 described above.

In operation, and as described in more detail herein, a compute device (e.g., the master controller 1602 or the orchestrator server 1604) of the system 1600 may facilitate establishing a hierarchical consensus among different subsystems (e.g., a data storage subsystem, an acceleration subsystem, etc. formed by the sleds 1610, 1612, 1614, 1616) in the system 1600. Doing so reduces the likelihood that management actions associated with one subsystem will override management actions associated with another subsystem (e.g., arising from a delay in one subsystem adapting to a set of control plane instructions (e.g., to enable resources in the subsystems to operate as a composed node) while other subsystems have adapted to the control plane instructions). In doing so, the compute device (e.g., the master controller 1602 or the orchestrator server 1604) determines latencies associated with each subsystem. Further, the compute device determines an amount of time needed for the subsystems to come to a consensus in response to a set of control plane instructions (e.g., to form a composed node). Additionally, the compute device may budget the determined amount of time into control plane instructions (e.g., suspending execution of a workload until the determined amount of time to reach a consensus has elapsed) and, in some embodiments, may determine configuration changes to reduce one or more of the latencies (e.g., to reduce the amount of time needed to reach a consensus). As such, the system 1600 may operate more efficiently than other disaggregated systems that do not take into account latencies of subsystems to adapt to a set of control plane instructions. Referring briefly to FIG. 21, components (e.g., subsystems) of the disaggregated system 2100, similar to the disaggregated system 1600, may communicate in a software defined network (SDN) to execute workloads (e.g., in one or more composed nodes).

Referring now to FIG. 17, a compute device (e.g., the master controller 1602 or the orchestrator server 1604) of the system 1600 may perform a method 1700 for providing latency-aware consensus management in the system 1600. For simplicity, the method 1700 is described herein as being performed by the master controller 1602. However, it should be understood that all or part of the method 1700 may be performed by another compute device (e.g., the orchestrator server 1604). The method 1700 begins with block 1702 in which the master controller 1602 determines whether to enable latency-aware consensus management. In the illustrative embodiment, the master controller 1602 may determine to enable latency-aware consensus management in response to a determination that a configuration setting (e.g., in memory) indicates to enable latency-aware consensus management. In other embodiments, the master controller 1602 may make the determination based on other factors. Regardless, in response to a determination to enable latency-aware consensus management, the method 1700 advances to block 1704 in which the master controller 1602 determines latencies associated with subsystems (e.g., the sleds 1610, 1612, 1615, 1616) of a disaggregated system (e.g., the system 1600). In doing so, and as indicated in block 1706, the master controller 1602 may determine a latency between the master controller and a host (e.g., the compute sled 1610). For example, and as indicated in block 1708, the master controller 1602 may determine a processing time that elapses for the host (e.g., the compute sled 1610) to send a packet in response to receiving a packet, as indicated in block 1708. The master controller 1602 may also determine an inbound latency associated with the host (e.g., the compute sled 1610). For example, and as indicated in block 1712, the master controller 1602 may determine an amount of time that elapses for a packet that is sent from one device (e.g., another compute device, such as another sled) to be received by the host (e.g., the compute sled 1610). The master controller 1602 may also determine an outbound latency associated with the host (e.g., the compute sled 1610), as indicated in block 1714. As indicated in block 1716, the master controller 1602 may determine a latency (e.g., an amount of time that elapses) to insert one or more rules into a content addressable memory. Further, and as indicated in block 1718, the master controller 1602 may determine a latency to insert, into a table (e.g., a software defined networking table in a content addressable memory), a rule that defines one or more operations to be performed in response to receipt of a packet that satisfies predefined criteria (e.g., one or more sets of data in a header or a payload of a packet that satisfies a reference criteria, such as destination address, a source address, a type of content in the payload, etc.). As indicated in block 1720, the master controller 1602 may determine a latency to insert, into a table, a burst of rules (e.g., a set of multiple rules) that each defines one or more operations to be performed in response to receipt of a packet that satisfies predefined criteria. Still referring to FIG. 17, the master controller 1602 may also determine a modification latency, as indicated in block 1722. For example, and as indicated in block 1724, the master controller 1602 may determine a latency for modifying a rule that defines one or more operations that are to be performed in response to receipt of a packet that satisfies predefined criteria. In determining the latencies in blocks 1706 through 1724, the master controller 1602 may request, from the host, data (e.g., telemetry data) that is indicative of the latencies incurred in performing the operations and analyze the received data to identify the latencies. In other embodiments, the master controller 1602 may obtain the data from another source (e.g., from the monitor server 1606 or the orchestrator server 1604 which may receive data indicative of the latencies and provide the data to the master controller 1602). In yet other embodiments, the master controller 1602 may obtain data indicative of the latencies from another source.

Referring now to FIG. 18, the master controller 1602 may also determine a multi-data owner latency, as indicated in block 1726. In doing so, and as indicated in block 1728, the master controller 1602 may determine a response time per received packet as a combination of twice the latency of a switch to controller communication and twice the latency of a controller to controller communication, expressed in Equation 1 below:

SDNT=2*delay[sw-ctrl]+2*delay[ctrl-ctrl]+2*delay[ctrl-ctrl]  (Equation 1)

In the model above (e.g., Equation 1), local decisions based on network interface controller (NIC) buffers and rule processing changes, guided by software defined networking table update improvements, may reduce the latencies in the subsystem, as described in more detail herein.

As indicated in block 1730, the master controller 1602 may determine a latency for an accelerator sled (e.g., the accelerator sled 1612) to process a packet. In doing so, and as indicated in block 1732, the master controller 1602 may determine a packet header processing time in which the accelerator sled 1612 determines the target accelerator device (e.g., an accelerator device 1622, 1624 on the accelerator sled 1612) that a received packet is to be provided to. As indicated in block 1734, the master controller 1602 may determine a processing time for a mailbox mapping of a memory address to a PCIe port address to be performed (e.g., mapping data written to a particular memory address to a PCIe port assigned to an accelerator device 1622, 1624, such as an FPGA). In block 1736, the master controller 1602 may determine a network interface controller (NIC) virtual Ethernet bridge (VEB) processing time (e.g., an amount of time to determine a path that a packet is to take). Additionally, and as indicated in block 1738, the master controller 1602 may determine a processing time for allocating memory on the accelerator sled 1612 to process a received packet (e.g., an amount of time to allocate memory to a particular accelerator device 1622, 1624 to process the packet). As indicated in block 1740, the master controller 1602 may determine a processing time for an accelerator device (e.g., an accelerator device 1622, 1624) on the accelerator sled 1612 to process a received packet (e.g., to perform an accelerated function, such as encryption, decryption, compression, decompression, produce an inference with a neural network, etc. on data in the payload of the packet). The master controller 1602 may also determine a latency for communications between accelerator devices (e.g., a latency to communicate a packet between the accelerator devices 1622, 1624 on the same accelerator sled 1612 or a latency to communicate a packet from an accelerator device on one accelerator sled to an accelerator device on another accelerator sled), as indicated in block 1742. As indicated in block 1744, the master controller 1602 may determine the total accelerator sled latency as a function of a switch port latency in combination with the processing times (e.g., latencies) from block 1732 through 1742. The master controller 1602 may determine the total latency associated with the accelerator sled (e.g., the accelerator sled 1612) using Equation 2, set forth below:

FPT=2*Switch port latency+(a+b+c)+2(d+e)+nf  (Equation 2)

In Equation 2 above, a is the latency from block 1732, b is the latency from block 1734, c is the latency from block 1736, d is the latency from block 1738, e is the latency from block 1740, and f is the latency from block 1742. Further, in Equation 2, n is the number of accelerator devices on the accelerator sled 1612. The master controller 1602 may determine the latencies above based on telemetry data provided by the accelerator sled 1612 (e.g., by receiving the telemetry data directly from the accelerator sled 1612 or by obtaining the telemetry data from another device (e.g., the monitor server 1606 or the orchestrator server 1604) that received the data from the accelerator sled 1612).

Referring now to FIG. 19, in block 1746 the master controller 1602 may additionally determine a latency associated with configuring (e.g., or reconfiguring) a host (e.g., the compute sled 1610). In doing so, and as indicated in block 1748, the master controller 1602 may determine a latency for a basic input output system (BIOS) and system management controller (SMC) (e.g., of the host) to configure the host (e.g., the compute sled 1610). In doing so, and as indicated in block 1750, the master controller 1602 may determine a time for a monitor (e.g., the monitor server 1606) to determine if a re-composition or configuration change in required. As indicated in block 1752, the master controller 1602 may determine a time (e.g., an amount of time that elapses) for a monitor (e.g., the monitor server 1606) to send a request to the system management controller (SMC). Further, and as indicated in block 1754, the master controller 1602 may determine a time (e.g., an amount of time that elapses) for the SMC to process the request (e.g., from block 1752) and determine the corresponding type of boot associated with the requested change (e.g., a cold boot, a warm boot, erase memory/storage, change hyper threading mode, change memory interleave settings, change memory mode such as volatile, two level memory, app-direct persistent memory, etc., online change without reboot, change boot target, etc.). Additionally, and as indicated in block 1756, the master controller 1602 may determine a time (e.g., an amount of time that elapses) for the SMC to commit an action. In some embodiments, the SMC may perform a commit itself, such as reconfiguring a processor or I/O register. In other embodiments, the SMC may communicate a request to the BIOS, a NIC, an SSD, an accelerator device (e.g., an FPGA), or other component. Further, and as indicated in block 1758, the master controller 1602 may determine a time (e.g., an amount of time that elapses) for the SMC to receive a response from one or more components (e.g., in response to the commit from block 1756) and send the response to the monitor server (e.g., to the monitor server 1606). As indicated in block 1760, the master controller 1602 may determine a time (e.g., an amount of time that elapses) for the host (e.g., the compute sled 1610) to complete a boot process (e.g., including handing off control to an operating system) and service requests. Additionally, the master controller 1602 may determine a BIOS-SMC latency, BST, according to Equation 3, provided below:

BIOS-SMC latency BST=T1+T2+T3  (Equation 3)

In Equation 3 above, T1 is the latency determined in block 1750, T2 is the latency determined in block 1752, and T3 is the latency determined in block 1754. The master controller 1602 may determine the latencies described above from telemetry data provided to the master controller (e.g., either directly from the component incurring the latencies or through an intermediary device, such as the orchestrator server 1604 or the monitor server 1606). As indicated in block 1762, master controller 1602 may determine a latency associated with a data storage subsystem (e.g., the data storage sled 1614). In doing so, the master controller 1602 may determine a data storage sled non-uniform memory access (NUMA) node response time (e.g., an amount of time for a set of processors assigned to a set of memory to write to or read from a requested memory address), as indicated in block 1764. As indicated in block 1766, the master controller 1602 may determine a storage driver read or write time (e.g., an amount of time reported by a driver used to access a data storage device 1626, 1628 to read from or write to the data storage device 1626, 1628). The master controller 1602 may also determine a time for a network driver to receive a data storage request and pass the request to a file system, as indicated in block 1768. As indicated in block 1770, the master controller 1602 may determine a cache access time (e.g., an amount of time that elapses for a cache of a data storage device 1626, 1628 to be read from or written to). Similarly, the master controller 1602 may determine a deduplication processing time (e.g., an amount of time that elapses for the data storage sled 1614 to determine that a set of data is already stored in a data storage device 1626, 1628 and to store a reference to that already-stored data rather than writing another copy of the data in the data storage device 1626, 1628), as indicated in block 1772. Additionally, the master controller 1602 may determine an amount of time consumed in performing a rebalancing operation (e.g., redistributing data storage operations across multiple data storage devices 1626, 1628) to maintain a target quality of service (e.g., to maintain a defined level of reliability, throughput, etc.), as indicated in block 1774. The master controller may determine a total storage latency, TSL, according to Equation 4, provided below:

TSL=2[T1+T2+T3+T4+T5]−T6  (Equation 4)

In Equation 4, above, T1 is the time from block 1764, T2 is the time from block 1766, T3 is the time from block 1768, T4 is the time from block 1770, T5 is the time from block 1772, and T6 is the time from block 1774.

Referring now to FIG. 20, the master controller 1602, in the illustrative embodiment, additionally determines, as a function of the determined latencies of the subsystems (e.g., from blocks 1704 through 1774) a time period in which a configuration change to the disaggregated system would reach a consistent state (e.g., when all of the subsystems have adapted to a configuration change), as indicated in block 1776. In doing so, and as indicated in block 1778, the master controller 1602 may determine a time to completion (TTC) (e.g., of a longest chain of actions performed in a subsystem to adapt to a given configuration change). As indicated in block 1780, the master controller 1602 may determine the time to reach a consistent state as the time to completion. As indicated in block 1782, the master controller 1602 may utilize a graph of actions and attempt to minimize (e.g., reduce) the time reach a consistent state among the subsystems affected by a given configuration change (e.g., by determining a set of actions in the graph that provides a consistent state among the subsystems in the least amount of time). The minimum time to completion may be determined as a combination of the minimum BST (e.g., from Equation 3), the minimum TSL (e.g., from Equation 4), and the minimum FPT (e.g., from Equation 2). Further, the minimum SDNT may be determined as a combination of the minimum FPT (from Equation 2) and the minimum TSL (e.g., from Equation 4). The time to reach a consensus among the subsystems of the disaggregated system 1600, in the illustrative embodiment, is the minimum TTC.

As indicated in block 1784, the master controller 1602 may apply a configuration change to one or more subsystems of the disaggregated system 1600 (e.g., by providing a corresponding request to each affected subsystem to perform a configuration change, such as a change to enable one or more of the components of the sleds 1610, 1612, 1614, 1616 to operate as a composed node to collectively execute a workload). In doing so, and as indicated in block 1786, the master controller 1602 may suspend operations in the disaggregated system 1600 until the determined time period to reach a consistent state has elapsed (e.g., until the TCC has elapsed). Additionally, and as indicated in block 1788, the master controller 1602 may apply changes to one or more subsystems of the disaggregated system 1600 to decrease a latency associated with the subsystem(s) (e.g., to reduce the TTC). As indicated in block 1790, the master controller 1602 may determine available table update latency improvements. In doing so, and as indicated in block 1792, the master controller 1602 may determine whether rules for a predefined type of network traffic (e.g., packets) can be processed before (e.g., prioritized over) other types of network traffic (e.g., by querying the corresponding subsystem that is to perform the processing to determine whether prioritization based on traffic type is supported). In the illustrative embodiment, the master controller 1602 may determine whether rules for storage related network traffic can be prioritized over other types of network traffic, as indicated in block 1794. If so, the master controller 1602 may apply the prioritization to reduce the latency in processing the traffic of that type (e.g., data storage traffic). As indicated in block 1796, the master controller 1602 may determine one or more memory configuration changes to decrease latency in an accelerator sled (e.g., the accelerator sled 1612). For example, and as indicated in block 1798, the master controller 1602 may enable shared memory access between an accelerator device (e.g., one or more of the accelerator devices 1622, 1624) and a network interface controller (NIC) of the accelerator sled 1612 (e.g., removing the need to copy data between separate memory regions used by the accelerator devices 1622, 1624 and the NIC). As indicated in block 1800, the master controller 1602 may determine changes to enable parallel processing of reconfiguration operations in the host (e.g., the compute sled 1610). The master controller 1602 may also determine changes in cache utilization, NUMA configuration, and/or quality of service (QoS) management in a storage drive (e.g., a data storage device 1626, 1628) of a data storage sled (e.g., the data storage sled 1614) to reduce a latency in performing data access operations on data storage sled (e.g., the data storage sled 1614), as indicated in block 1802. Subsequently, the method 1700 loops back to block 1702 in which the master controller 1602 may re-determine latencies in the subsystems of the disaggregated system 1600 and potentially perform additional configuration changes to one or more of the subsystems.

Examples

Illustrative examples of the technologies disclosed herein are provided below. An embodiment of the technologies may include any one or more, and any combination of, the examples described below.

Example 1 includes a compute device comprising circuitry to determine latencies associated with subsystems of a disaggregated system; and determine, as a function of the determined latencies, a time period in which a configuration change to the disaggregated system is to reach a consistent state in the subsystems.

Example 2 includes the subject matter of Example 1, and wherein the circuitry is further to apply the configuration change to one or more of the subsystems.

Example 3 includes the subject matter of any of Examples 1 and 2, and wherein the circuitry is further to suspend operations of the subsystems for the determined time period.

Example 4 includes the subject matter of any of Examples 1-3, and wherein the circuitry is further to apply a change to one of the subsystems to decrease a latency of the subsystem.

Example 5 includes the subject matter of any of Examples 1-4, and wherein the circuitry is further to determine whether rules for storage related network traffic can be prioritized over other types of network traffic; and prioritize, in response to a determination that rules for storage related network traffic can be prioritized over other types of network traffic, the rules for storage related network traffic.

Example 6 includes the subject matter of any of Examples 1-5, and wherein the circuitry is further to determine memory configuration changes to decrease latency in an accelerator sled.

Example 7 includes the subject matter of any of Examples 1-6, and wherein the circuitry is further to enable an accelerator device and a network interface controller of the accelerator sled to share memory.

Example 8 includes the subject matter of any of Examples 1-7, and wherein the circuitry is further to enable parallel processing of reconfiguration operations in a host.

Example 9 includes the subject matter of any of Examples 1-8, and wherein the circuitry is further to determine changes in cache utilization, non-uniform memory access, or quality of service management in a data storage sled to decrease the latency of operations performed by the data storage sled.

Example 10 includes the subject matter of any of Examples 1-9, and wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency between a master controller and a host of the disaggregated system.

Example 11 includes the subject matter of any of Examples 1-10, and wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a processing time for a host to send a packet in response to receiving a packet.

Example 12 includes the subject matter of any of Examples 1-11, and wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency to insert a rule into a content addressable memory.

Example 13 includes the subject matter of any of Examples 1-12, and wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency for modifying a rule that defines an operation to be performed in response to receipt of a packet that satisfies predefined criteria.

Example 14 includes the subject matter of any of Examples 1-13, and wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a multi-data owner latency.

Example 15 includes the subject matter of any of Examples 1-14, and wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency for an accelerator sled to process a packet.

Example 16 includes the subject matter of any of Examples 1-15, and wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency to configure a host.

Example 17 includes the subject matter of any of Examples 1-16, and wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency associated with a data storage subsystem.

Example 18 includes one or more machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a compute device to determine latencies associated with subsystems of a disaggregated system; and determine, as a function of the determined latencies, a time period in which a configuration change to the disaggregated system is to reach a consistent state in the subsystems.

Example 19 includes the subject matter of Example 18, and wherein the instructions further cause the compute device to apply a change to one of the subsystems to decrease a latency of the subsystem.

Example 20 includes a method comprising determining, by a compute device, latencies associated with subsystems of a disaggregated system; and determining, by a compute device and as a function of the determined latencies, a time period in which a configuration change to the disaggregated system is to reach a consistent state in the subsystems. 

1. A compute device comprising: circuitry to: determine latencies associated with subsystems of a disaggregated system; and determine, as a function of the determined latencies, a time period in which a configuration change to the disaggregated system is to reach a consistent state in the subsystems.
 2. The compute device of claim 1, wherein the circuitry is further to apply the configuration change to one or more of the subsystems.
 3. The compute device of claim 2, wherein the circuitry is further to suspend operations of the subsystems for the determined time period.
 4. The compute device of claim 1, wherein the circuitry is further to apply a change to one of the subsystems to decrease a latency of the subsystem.
 5. The compute device of claim 4, wherein the circuitry is further to: determine whether rules for storage related network traffic can be prioritized over other types of network traffic; and prioritize, in response to a determination that rules for storage related network traffic can be prioritized over other types of network traffic, the rules for storage related network traffic.
 6. The compute device of claim 4, wherein the circuitry is further to determine memory configuration changes to decrease latency in an accelerator sled.
 7. The compute device of claim 6, wherein the circuitry is further to enable an accelerator device and a network interface controller of the accelerator sled to share memory.
 8. The compute device of claim 4, wherein the circuitry is further to enable parallel processing of reconfiguration operations in a host.
 9. The compute device of claim 4, wherein the circuitry is further to determine changes in cache utilization, non-uniform memory access, or quality of service management in a data storage sled to decrease the latency of operations performed by the data storage sled.
 10. The compute device of claim 1, wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency between a master controller and a host of the disaggregated system.
 11. The compute device of claim 10, wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a processing time for a host to send a packet in response to receiving a packet.
 12. The compute device of claim 10, wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency to insert a rule into a content addressable memory.
 13. The compute device of claim 10, wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency for modifying a rule that defines an operation to be performed in response to receipt of a packet that satisfies predefined criteria.
 14. The compute device of claim 1, wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a multi-data owner latency.
 15. The compute device of claim 1, wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency for an accelerator sled to process a packet.
 16. The compute device of claim 1, wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency to configure a host.
 17. The compute device of claim 1, wherein to determine latencies associated with subsystems of the disaggregated system comprises to determine a latency associated with a data storage subsystem.
 18. One or more machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a compute device to: determine latencies associated with subsystems of a disaggregated system; and determine, as a function of the determined latencies, a time period in which a configuration change to the disaggregated system is to reach a consistent state in the subsystems.
 19. The one or more machine-readable storage media of claim 18, wherein the instructions further cause the compute device to apply a change to one of the subsystems to decrease a latency of the subsystem.
 20. A method comprising: determining, by a compute device, latencies associated with subsystems of a disaggregated system; and determining, by a compute device and as a function of the determined latencies, a time period in which a configuration change to the disaggregated system is to reach a consistent state in the subsystems. 